Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cc8cce6ea0326f9a6e6cbaf6ed98e2ecc089ed0fd6bd88bcd3ef205e77dbce7

Tx prefix hash: 87701146ca670d7946abed0ad7ba6974329c891332ca0a83e9fd3f65450dc0e5
Tx public key: 337ba68d9ea6223718e25728675624e6f7b52235892689e39594a8a44aae4880
Timestamp: 1718700732 Timestamp [UCT]: 2024-06-18 08:52:12 Age [y:d:h:m:s]: 00:287:22:09:35
Block: 1046790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205727 RingCT/type: yes/0
Extra: 01337ba68d9ea6223718e25728675624e6f7b52235892689e39594a8a44aae488002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 417e7c45696a1f9cc74bd6e870e847ce0c05c451d91237ed21fa9f324cc7fab5 0.600000000000 1516609 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": 1046800, "vin": [ { "gen": { "height": 1046790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "417e7c45696a1f9cc74bd6e870e847ce0c05c451d91237ed21fa9f324cc7fab5" } } ], "extra": [ 1, 51, 123, 166, 141, 158, 166, 34, 55, 24, 226, 87, 40, 103, 86, 36, 230, 247, 181, 34, 53, 137, 38, 137, 227, 149, 148, 168, 164, 74, 174, 72, 128, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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