Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7807f3f873f995dfb13bd766c0c796e6242e780a7f6f0cd5a003b871acd2649

Tx prefix hash: c295e2a752c64d4e1a58f12d7cd95856085596491cd94a248d198223be8b8ed2
Tx public key: 56a242480efa783e46759dfd769e8370ac6b919501cd3a2cfe83d7227639b42e
Timestamp: 1713946495 Timestamp [UCT]: 2024-04-24 08:14:55 Age [y:d:h:m:s]: 00:200:18:36:54
Block: 1007375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143727 RingCT/type: yes/0
Extra: 0156a242480efa783e46759dfd769e8370ac6b919501cd3a2cfe83d7227639b42e0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17b1f2aa9d97764a97a1bbe0c318ce2b1aab844d245fa3613b33b1a31527b584 0.600000000000 1468695 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": 1007385, "vin": [ { "gen": { "height": 1007375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17b1f2aa9d97764a97a1bbe0c318ce2b1aab844d245fa3613b33b1a31527b584" } } ], "extra": [ 1, 86, 162, 66, 72, 14, 250, 120, 62, 70, 117, 157, 253, 118, 158, 131, 112, 172, 107, 145, 149, 1, 205, 58, 44, 254, 131, 215, 34, 118, 57, 180, 46, 2, 17, 0, 0, 0, 8, 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