Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c5ea8fc02175b778c8d9656840f750517ed31cd6aa22f55becfee4a7b49eebb

Tx prefix hash: 63d1e974b7bc23d1f14b4ffc96084e77d09e3a52ffb4dc94a35cff4f547b8625
Tx public key: 1dcdcc4c6280ae58f7e14f44c6afdabe39950d6beb13230be39a0645bdd60b00
Timestamp: 1716725454 Timestamp [UCT]: 2024-05-26 12:10:54 Age [y:d:h:m:s]: 00:313:04:12:18
Block: 1030417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223824 RingCT/type: yes/0
Extra: 011dcdcc4c6280ae58f7e14f44c6afdabe39950d6beb13230be39a0645bdd60b000211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53296fdd207db314869f8b514c7fcf803f5fe58ac7597c5e42f644e82e61eae1 0.600000000000 1498672 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": 1030427, "vin": [ { "gen": { "height": 1030417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53296fdd207db314869f8b514c7fcf803f5fe58ac7597c5e42f644e82e61eae1" } } ], "extra": [ 1, 29, 205, 204, 76, 98, 128, 174, 88, 247, 225, 79, 68, 198, 175, 218, 190, 57, 149, 13, 107, 235, 19, 35, 11, 227, 154, 6, 69, 189, 214, 11, 0, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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