Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a72c167eef8b7cacfa1f8822c916c6fc1b4eab9cd755cc3ce5099533a3d66d72

Tx prefix hash: 8eb77f48f618958a8c86b96e0b2b2252e96090e3c853ed98f216c96bffd49ffe
Tx public key: fbe65cb00339fa0025c6a60f10cc5cdef86236111c7ad1428c7e5926f8e56133
Timestamp: 1713994034 Timestamp [UCT]: 2024-04-24 21:27:14 Age [y:d:h:m:s]: 01:056:03:50:26
Block: 1007765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300960 RingCT/type: yes/0
Extra: 01fbe65cb00339fa0025c6a60f10cc5cdef86236111c7ad1428c7e5926f8e561330211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1735ee65c79ee27ca503c079d3f28ce9a88066e7f4c5673ab870ff514b37c92 0.600000000000 1469209 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": 1007775, "vin": [ { "gen": { "height": 1007765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1735ee65c79ee27ca503c079d3f28ce9a88066e7f4c5673ab870ff514b37c92" } } ], "extra": [ 1, 251, 230, 92, 176, 3, 57, 250, 0, 37, 198, 166, 15, 16, 204, 92, 222, 248, 98, 54, 17, 28, 122, 209, 66, 140, 126, 89, 38, 248, 229, 97, 51, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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