Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0213069f95c6e2f5b8d480d832a5d68008e81efc9db12fea402b514b10324fc6

Tx prefix hash: 002ceec16174f5ee331887a2645c6b33c136f61b62e4fd3d1bdbf6bfb30ff3ac
Tx public key: db70cb8a0dfa32a54ea4bbecf73e60c3e6bfb5d56774b183dce8d1f7f9911ec6
Timestamp: 1747730647 Timestamp [UCT]: 2025-05-20 08:44:07 Age [y:d:h:m:s]: 00:245:14:05:25
Block: 1286925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173159 RingCT/type: yes/0
Extra: 01db70cb8a0dfa32a54ea4bbecf73e60c3e6bfb5d56774b183dce8d1f7f9911ec60211000000099f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85f2d813fb312ace001e1c61ae131acf90befac8dced0f3f26141e84e692c1d0 0.600000000000 1774392 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": 1286935, "vin": [ { "gen": { "height": 1286925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85f2d813fb312ace001e1c61ae131acf90befac8dced0f3f26141e84e692c1d0" } } ], "extra": [ 1, 219, 112, 203, 138, 13, 250, 50, 165, 78, 164, 187, 236, 247, 62, 96, 195, 230, 191, 181, 213, 103, 116, 177, 131, 220, 232, 209, 247, 249, 145, 30, 198, 2, 17, 0, 0, 0, 9, 159, 159, 230, 140, 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