Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 179d073f240194f813481f696a892719954d5923c84fd323d7beea7cc8dc4abe

Tx prefix hash: 528357b41a66cf2ee21bcef031c79dc4724890721e0534060f2d4fc01d047e39
Tx public key: 8fed7a5d693f676edc483c8ba0df846d5e9d3b1eed779e19f78d5f4bd018d58d
Timestamp: 1721245142 Timestamp [UCT]: 2024-07-17 19:39:02 Age [y:d:h:m:s]: 00:308:06:37:03
Block: 1067887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220288 RingCT/type: yes/0
Extra: 018fed7a5d693f676edc483c8ba0df846d5e9d3b1eed779e19f78d5f4bd018d58d02110000001591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eede0b22a0dedca1cb23d67ff184dd109016896ee75d57eb6e71148569c577c9 0.600000000000 1538824 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": 1067897, "vin": [ { "gen": { "height": 1067887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eede0b22a0dedca1cb23d67ff184dd109016896ee75d57eb6e71148569c577c9" } } ], "extra": [ 1, 143, 237, 122, 93, 105, 63, 103, 110, 220, 72, 60, 139, 160, 223, 132, 109, 94, 157, 59, 30, 237, 119, 158, 25, 247, 141, 95, 75, 208, 24, 213, 141, 2, 17, 0, 0, 0, 21, 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