Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 067e84d91428307f10c4cbc6dcac0d6c4d8b18f7345828f121de6c6455681697

Tx prefix hash: 12ec341aa4dac0deb6f2704a7f6e802e61b54a34148d1401d7029ca45cd6029e
Tx public key: 1d030ab738ca25a174c63f7054c36c30f6c51a9a8d67d00f4ee581ff9aab6c59
Timestamp: 1583238470 Timestamp [UCT]: 2020-03-03 12:27:50 Age [y:d:h:m:s]: 04:364:05:53:40
Block: 75602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154373 RingCT/type: yes/0
Extra: 011d030ab738ca25a174c63f7054c36c30f6c51a9a8d67d00f4ee581ff9aab6c590211000000ba724f989b000000000000000000

1 output(s) for total of 344.746595862000 dcy

stealth address amount amount idx
00: 2326e1db73451ffbbba4b1da91dc6e6f4bf921d9edcae8b613f1e9e3ea17e9a2 344.746595862000 139556 of 0

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": 75612, "vin": [ { "gen": { "height": 75602 } } ], "vout": [ { "amount": 344746595862, "target": { "key": "2326e1db73451ffbbba4b1da91dc6e6f4bf921d9edcae8b613f1e9e3ea17e9a2" } } ], "extra": [ 1, 29, 3, 10, 183, 56, 202, 37, 161, 116, 198, 63, 112, 84, 195, 108, 48, 246, 197, 26, 154, 141, 103, 208, 15, 78, 229, 129, 255, 154, 171, 108, 89, 2, 17, 0, 0, 0, 186, 114, 79, 152, 155, 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