Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2f25f3acb690e870ad32b87d6c497ee64dcd3c4c349f9f9321bfd0a633750e5

Tx prefix hash: 98773ad176fe001aafd0949b0494be99d806576275e0d827b045d51b7b97f85f
Tx public key: b41113c47cb8857c312310c86d4ef3393fd7228d54a726e6bd10c0ef0e158d75
Timestamp: 1718542042 Timestamp [UCT]: 2024-06-16 12:47:22 Age [y:d:h:m:s]: 00:333:03:38:57
Block: 1045485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238084 RingCT/type: yes/0
Extra: 01b41113c47cb8857c312310c86d4ef3393fd7228d54a726e6bd10c0ef0e158d7502110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d44d8cf49cde79d5a75f4f2587bd442c532351e6d1f0481aaba7aef46f955aea 0.600000000000 1515068 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": 1045495, "vin": [ { "gen": { "height": 1045485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d44d8cf49cde79d5a75f4f2587bd442c532351e6d1f0481aaba7aef46f955aea" } } ], "extra": [ 1, 180, 17, 19, 196, 124, 184, 133, 124, 49, 35, 16, 200, 109, 78, 243, 57, 63, 215, 34, 141, 84, 167, 38, 230, 189, 16, 192, 239, 14, 21, 141, 117, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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