Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b60d7aef0df2042150f3613838fc72c73c0a2bf3f4adf771124b6a7338e5c205

Tx prefix hash: 26bc5aafd959eb295e1fbe2dcc7b635c7f2a2f758ace41d24a7881adf08c80a0
Tx public key: 9417813964287f5eff9f9a07724b2da8d53b5b4ec5aff98bfe73dc0a0b7fc22d
Timestamp: 1763882208 Timestamp [UCT]: 2025-11-23 07:16:48 Age [y:d:h:m:s]: 00:004:13:40:12
Block: 1418233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3275 RingCT/type: yes/0
Extra: 019417813964287f5eff9f9a07724b2da8d53b5b4ec5aff98bfe73dc0a0b7fc22d02110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d384f4ca1a898c494db003727a681ecb7142f2eceabe6437194d1fd8c2c2286 0.600000000000 1906762 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1418243, "vin": [ { "gen": { "height": 1418233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d384f4ca1a898c494db003727a681ecb7142f2eceabe6437194d1fd8c2c2286" } } ], "extra": [ 1, 148, 23, 129, 57, 100, 40, 127, 94, 255, 159, 154, 7, 114, 75, 45, 168, 213, 59, 91, 78, 197, 175, 249, 139, 254, 115, 220, 10, 11, 127, 194, 45, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8