Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2209952bd2963ac7b6479a9ce29d573a48e92624e8972238ac3f1369588abac5

Tx prefix hash: 33e8c0ed138f190a9c754623dd5a3f070c7fa15a08e848f915b179254cd64f84
Tx public key: 46a1aa7c9921cf2cfa4751c4c7ec8c2204514ed5cfe7aee0a62755ef43e0f424
Timestamp: 1709109872 Timestamp [UCT]: 2024-02-28 08:44:32 Age [y:d:h:m:s]: 01:262:10:43:51
Block: 967276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446307 RingCT/type: yes/0
Extra: 0146a1aa7c9921cf2cfa4751c4c7ec8c2204514ed5cfe7aee0a62755ef43e0f424021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdee8d360c1be42588f5aa24c278a4838f1f42551adfbff187d442f85ce05bf7 0.600000000000 1427053 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": 967286, "vin": [ { "gen": { "height": 967276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdee8d360c1be42588f5aa24c278a4838f1f42551adfbff187d442f85ce05bf7" } } ], "extra": [ 1, 70, 161, 170, 124, 153, 33, 207, 44, 250, 71, 81, 196, 199, 236, 140, 34, 4, 81, 78, 213, 207, 231, 174, 224, 166, 39, 85, 239, 67, 224, 244, 36, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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