Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe1d4768636fabca5905f373cff531a25e79083054b2a7025569094f74c00a14

Tx prefix hash: 0da858fdda7129e9569debc79944435b6d3a603706a4de1924590e9f6f2ea51b
Tx public key: b73afbca1e827e4f6c9616e4a561ee23ae53d4e144891c898edcb8c8e78f4096
Timestamp: 1672684368 Timestamp [UCT]: 2023-01-02 18:32:48 Age [y:d:h:m:s]: 02:016:05:03:37
Block: 666150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 533497 RingCT/type: yes/0
Extra: 01b73afbca1e827e4f6c9616e4a561ee23ae53d4e144891c898edcb8c8e78f4096021100000001272bcc39000000000000000000

1 output(s) for total of 3.808627342000 dcy

stealth address amount amount idx
00: a1e44fc400cd0186242aefabbb496be55bc313848f7cdaa65e1a8db6541d24e2 3.808627342000 1107249 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": 666160, "vin": [ { "gen": { "height": 666150 } } ], "vout": [ { "amount": 3808627342, "target": { "key": "a1e44fc400cd0186242aefabbb496be55bc313848f7cdaa65e1a8db6541d24e2" } } ], "extra": [ 1, 183, 58, 251, 202, 30, 130, 126, 79, 108, 150, 22, 228, 165, 97, 238, 35, 174, 83, 212, 225, 68, 137, 28, 137, 142, 220, 184, 200, 231, 143, 64, 150, 2, 17, 0, 0, 0, 1, 39, 43, 204, 57, 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