Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb84fdd994ca550fe124de59ea0d086c5c5b8c651dd2bb16ca1f71809ad7d07b

Tx prefix hash: 2a2d8e07e85338e72af9ee8e77ecbfc207f20a01a71d2efa57766a2cac89d422
Tx public key: 6c9ae12ca9327d54a4404969f453b1b685e1cdfe6ad0bd87cb05a3f477c41e41
Timestamp: 1711110590 Timestamp [UCT]: 2024-03-22 12:29:50 Age [y:d:h:m:s]: 01:019:04:00:44
Block: 983883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274651 RingCT/type: yes/0
Extra: 016c9ae12ca9327d54a4404969f453b1b685e1cdfe6ad0bd87cb05a3f477c41e410211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1067c65414468f38678e8288596293a78048adf28423a74aaefacd1d598a2604 0.600000000000 1444036 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": 983893, "vin": [ { "gen": { "height": 983883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1067c65414468f38678e8288596293a78048adf28423a74aaefacd1d598a2604" } } ], "extra": [ 1, 108, 154, 225, 44, 169, 50, 125, 84, 164, 64, 73, 105, 244, 83, 177, 182, 133, 225, 205, 254, 106, 208, 189, 135, 203, 5, 163, 244, 119, 196, 30, 65, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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