Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c547ed9e2dd6fd0478db79d1a6015d272bc77c46a8562480b0bf357149fd145a

Tx prefix hash: 810d804dc06b94cbfb1c5fc60749e2f21fef0a784b7334931f4ff6dae2d907e7
Tx public key: 419925c9d760326d549b78b789aa0ec79cdb793b521f600114ab7b0009bc360c
Timestamp: 1749697739 Timestamp [UCT]: 2025-06-12 03:08:59 Age [y:d:h:m:s]: 00:150:05:20:18
Block: 1303177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105064 RingCT/type: yes/0
Extra: 01419925c9d760326d549b78b789aa0ec79cdb793b521f600114ab7b0009bc360c02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc42a229a8e57d87e6af996b8e13c74f6ec3bd3d7ed9fd10e987ac8c23b3fb38 0.600000000000 1790752 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": 1303187, "vin": [ { "gen": { "height": 1303177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc42a229a8e57d87e6af996b8e13c74f6ec3bd3d7ed9fd10e987ac8c23b3fb38" } } ], "extra": [ 1, 65, 153, 37, 201, 215, 96, 50, 109, 84, 155, 120, 183, 137, 170, 14, 199, 156, 219, 121, 59, 82, 31, 96, 1, 20, 171, 123, 0, 9, 188, 54, 12, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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