Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8174aad75450654531514990616a112a73267f9cfe182d82c76a5f23717080b6

Tx prefix hash: ab18dce257c59641fc518cbca1b38fd38bd8616316fe395ba4cc0c35b81b865e
Tx public key: dc9f1c8159b435099ee4f8dc7d30492218a048ba30247fe9b6676fa7397a289a
Timestamp: 1670706976 Timestamp [UCT]: 2022-12-10 21:16:16 Age [y:d:h:m:s]: 02:080:23:13:29
Block: 649788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579535 RingCT/type: yes/0
Extra: 01dc9f1c8159b435099ee4f8dc7d30492218a048ba30247fe9b6676fa7397a289a02110000000175e3f0e9000000000000000000

1 output(s) for total of 4.315017914000 dcy

stealth address amount amount idx
00: f593a7fe8b10b419f8b38c3c533c827e1f6a029080628dde6c746a55f101bb74 4.315017914000 1090157 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": 649798, "vin": [ { "gen": { "height": 649788 } } ], "vout": [ { "amount": 4315017914, "target": { "key": "f593a7fe8b10b419f8b38c3c533c827e1f6a029080628dde6c746a55f101bb74" } } ], "extra": [ 1, 220, 159, 28, 129, 89, 180, 53, 9, 158, 228, 248, 220, 125, 48, 73, 34, 24, 160, 72, 186, 48, 36, 127, 233, 182, 103, 111, 167, 57, 122, 40, 154, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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