Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aafb1c36791ddb1f743f01424e25ecbcfef18cde771daa842844a75caa19c95

Tx prefix hash: 37811a7265616a8b50a5147b5a9a42d5a859c2b9134529349af8f9da5789dd36
Tx public key: 46ed0f3fa4f94b5de841c4e55627e2305a042bde4cc02532b05a48a0e34f22d4
Timestamp: 1730154918 Timestamp [UCT]: 2024-10-28 22:35:18 Age [y:d:h:m:s]: 00:231:18:59:56
Block: 1141674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165430 RingCT/type: yes/0
Extra: 0146ed0f3fa4f94b5de841c4e55627e2305a042bde4cc02532b05a48a0e34f22d40211000000033cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a945eb31d29cee4c3baf80796f5c4751df1325913264448b1201adac84c3245 0.600000000000 1625485 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": 1141684, "vin": [ { "gen": { "height": 1141674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a945eb31d29cee4c3baf80796f5c4751df1325913264448b1201adac84c3245" } } ], "extra": [ 1, 70, 237, 15, 63, 164, 249, 75, 93, 232, 65, 196, 229, 86, 39, 226, 48, 90, 4, 43, 222, 76, 192, 37, 50, 176, 90, 72, 160, 227, 79, 34, 212, 2, 17, 0, 0, 0, 3, 60, 208, 252, 6, 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