Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cfbd20b7c620119512f75c451caa4edbca0a7ce5275e8362e7bd8693870faf1

Tx prefix hash: 7180001a1297ba927fb2b868018b33cf51be502a45fdfc79e4d8094fa726fc60
Tx public key: 3c364a2815e5be63075eb8ec448e2923f5ec413e1e2bb139617ef3a7dd6d7466
Timestamp: 1706421281 Timestamp [UCT]: 2024-01-28 05:54:41 Age [y:d:h:m:s]: 01:028:05:44:43
Block: 944957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281236 RingCT/type: yes/0
Extra: 013c364a2815e5be63075eb8ec448e2923f5ec413e1e2bb139617ef3a7dd6d746602110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52cc89bd5f02e3ea112b699ce0526cce6f59f386a2d773a30babf9d089f7f778 0.600000000000 1403259 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": 944967, "vin": [ { "gen": { "height": 944957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52cc89bd5f02e3ea112b699ce0526cce6f59f386a2d773a30babf9d089f7f778" } } ], "extra": [ 1, 60, 54, 74, 40, 21, 229, 190, 99, 7, 94, 184, 236, 68, 142, 41, 35, 245, 236, 65, 62, 30, 43, 177, 57, 97, 126, 243, 167, 221, 109, 116, 102, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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