Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5851318c9112d97c7053c4034d4664c01f174040edd2307aa17ec32f85829ce2

Tx prefix hash: 0309c8b6f7e8a9f8d3b73b304fdb7e186bff48da990b22eb73de7b1ea537666a
Tx public key: 8d08884d8adff404e4c324dbb36edfbf26c5716351833c3a86c3272db276ee45
Timestamp: 1681256043 Timestamp [UCT]: 2023-04-11 23:34:03 Age [y:d:h:m:s]: 01:275:15:07:19
Block: 736578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458514 RingCT/type: yes/0
Extra: 018d08884d8adff404e4c324dbb36edfbf26c5716351833c3a86c3272db276ee450211000000015029cbac000000000000000000

1 output(s) for total of 2.225417714000 dcy

stealth address amount amount idx
00: 1e636bfabe7a15c58d2f22fd0f91ecfcfcb49e65b4dc712e54f0ad33ce80f9ed 2.225417714000 1183031 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": 736588, "vin": [ { "gen": { "height": 736578 } } ], "vout": [ { "amount": 2225417714, "target": { "key": "1e636bfabe7a15c58d2f22fd0f91ecfcfcb49e65b4dc712e54f0ad33ce80f9ed" } } ], "extra": [ 1, 141, 8, 136, 77, 138, 223, 244, 4, 228, 195, 36, 219, 179, 110, 223, 191, 38, 197, 113, 99, 81, 131, 60, 58, 134, 195, 39, 45, 178, 118, 238, 69, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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