Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a46b3ec60be750e1a68cca421de4d5b8a70f0d1e02d30acb95079cb34c838f06

Tx prefix hash: 35fffefe85b11da1c39fd8926c1c961de08bdc2564a48474afe7b4f6e5188379
Tx public key: feff376c3eb5c441849f3a54ea3ec9e2156b79e80bfa11f4cf3e5459937690ac
Timestamp: 1736603933 Timestamp [UCT]: 2025-01-11 13:58:53 Age [y:d:h:m:s]: 00:107:15:14:10
Block: 1195062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76739 RingCT/type: yes/0
Extra: 01feff376c3eb5c441849f3a54ea3ec9e2156b79e80bfa11f4cf3e5459937690ac0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc49931c402c9b6b05bbca65885d30b8be8eb2a4ab8098603bd74adf9dfae616 0.600000000000 1681647 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": 1195072, "vin": [ { "gen": { "height": 1195062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc49931c402c9b6b05bbca65885d30b8be8eb2a4ab8098603bd74adf9dfae616" } } ], "extra": [ 1, 254, 255, 55, 108, 62, 181, 196, 65, 132, 159, 58, 84, 234, 62, 201, 226, 21, 107, 121, 232, 11, 250, 17, 244, 207, 62, 84, 89, 147, 118, 144, 172, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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