Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f256f2da9da2c9cb5ceefd54067c7ac46547625168d5bb083ff1ba1ac77e9b18

Tx prefix hash: e582c88481a3a694fc2f3a1ce0752c351931845f0ff47118056c1c56da08ac67
Tx public key: be8c49ec0886e318fe52dfb867cc1f832c4c5ef5f45bb129237d17c74f4908b5
Timestamp: 1732807490 Timestamp [UCT]: 2024-11-28 15:24:50 Age [y:d:h:m:s]: 00:113:20:41:11
Block: 1163647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81171 RingCT/type: yes/0
Extra: 01be8c49ec0886e318fe52dfb867cc1f832c4c5ef5f45bb129237d17c74f4908b50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2f54595888ed3fe8622679a077d877b324f952dd1d27bb34d9eaaeabe08bfa5 0.600000000000 1649314 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": 1163657, "vin": [ { "gen": { "height": 1163647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2f54595888ed3fe8622679a077d877b324f952dd1d27bb34d9eaaeabe08bfa5" } } ], "extra": [ 1, 190, 140, 73, 236, 8, 134, 227, 24, 254, 82, 223, 184, 103, 204, 31, 131, 44, 76, 94, 245, 244, 91, 177, 41, 35, 125, 23, 199, 79, 73, 8, 181, 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