Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0aaa63452ffbca4e50a3644ff23cde8d5a36e4d2a0d5d09707d996f7bf9b5019

Tx prefix hash: 7aff387c21a7a7976b6a10b070cabe818aee5004a6f96ecad580db0bb2b44c2d
Tx public key: f6ad90d23ca05c2ee97b7c9d1a2fc273adbc62ab042021770bbd67332c50fe2c
Timestamp: 1702339173 Timestamp [UCT]: 2023-12-11 23:59:33 Age [y:d:h:m:s]: 01:358:01:04:57
Block: 911145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514778 RingCT/type: yes/0
Extra: 01f6ad90d23ca05c2ee97b7c9d1a2fc273adbc62ab042021770bbd67332c50fe2c021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04e94215c8223461b427e3bda67ea0b90084a7c0b0a8bdba743333c3148a403a 0.600000000000 1368326 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": 911155, "vin": [ { "gen": { "height": 911145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04e94215c8223461b427e3bda67ea0b90084a7c0b0a8bdba743333c3148a403a" } } ], "extra": [ 1, 246, 173, 144, 210, 60, 160, 92, 46, 233, 123, 124, 157, 26, 47, 194, 115, 173, 188, 98, 171, 4, 32, 33, 119, 11, 189, 103, 51, 44, 80, 254, 44, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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