Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dad067d7d3f92849d14935651be08d0de1c69ac3bc747c6aaff99d52cbdb6651

Tx prefix hash: 7f547b97ff6304a3b1bd21fd5729c7f4502d9b24453c624a19f11e3d62222470
Tx public key: 1142be46af18233cd0cf6021ad6ae992d3c85895dc151a1ce4e50a4c55817e63
Timestamp: 1720805945 Timestamp [UCT]: 2024-07-12 17:39:05 Age [y:d:h:m:s]: 00:305:18:42:55
Block: 1064248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218495 RingCT/type: yes/0
Extra: 011142be46af18233cd0cf6021ad6ae992d3c85895dc151a1ce4e50a4c55817e6302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f996de626afcc0ea0fd7cc7c5ec6b0bb2dc269ea86930f1bc672cf40836b8d8 0.600000000000 1534771 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": 1064258, "vin": [ { "gen": { "height": 1064248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f996de626afcc0ea0fd7cc7c5ec6b0bb2dc269ea86930f1bc672cf40836b8d8" } } ], "extra": [ 1, 17, 66, 190, 70, 175, 24, 35, 60, 208, 207, 96, 33, 173, 106, 233, 146, 211, 200, 88, 149, 220, 21, 26, 28, 228, 229, 10, 76, 85, 129, 126, 99, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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