Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47e58061dc861c8a51821733fc6fa6b0908697efc79859ea69cbed4eea702311

Tx prefix hash: e9a78d8f1c594fbaa1f3e71ee62204341cd022c972e688b0f8723c168ed22c3f
Tx public key: a3f174f56e46c2a5993418cc26ea61ee01b30dc05ef23c5be002381f01d39ef0
Timestamp: 1629980533 Timestamp [UCT]: 2021-08-26 12:22:13 Age [y:d:h:m:s]: 03:074:11:07:02
Block: 321147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 827703 RingCT/type: yes/0
Extra: 01a3f174f56e46c2a5993418cc26ea61ee01b30dc05ef23c5be002381f01d39ef002110000000fdeae9d30000000000000000000

1 output(s) for total of 52.955019714000 dcy

stealth address amount amount idx
00: 000eeafbdaa0c1d5417cd71dae3024d333a688ed8a31c2522742c9d68e1def01 52.955019714000 666792 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": 321157, "vin": [ { "gen": { "height": 321147 } } ], "vout": [ { "amount": 52955019714, "target": { "key": "000eeafbdaa0c1d5417cd71dae3024d333a688ed8a31c2522742c9d68e1def01" } } ], "extra": [ 1, 163, 241, 116, 245, 110, 70, 194, 165, 153, 52, 24, 204, 38, 234, 97, 238, 1, 179, 13, 192, 94, 242, 60, 91, 224, 2, 56, 31, 1, 211, 158, 240, 2, 17, 0, 0, 0, 15, 222, 174, 157, 48, 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