Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 013b10fb653a6446f4129b5c783b5c2ebedb3a994812e7f605c96cd1391934b8

Tx prefix hash: 3c1f5317b4ac21872cc058a28f67a05eaa751daa04c753082dd92219d70da2b4
Tx public key: 0b5e4074d25744c1035139807a73e8019f640a281a6c48b0d9470797bbf4a0bc
Timestamp: 1725983748 Timestamp [UCT]: 2024-09-10 15:55:48 Age [y:d:h:m:s]: 00:274:22:28:03
Block: 1107167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196340 RingCT/type: yes/0
Extra: 010b5e4074d25744c1035139807a73e8019f640a281a6c48b0d9470797bbf4a0bc02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acdb6928dc547e10f9f5aae5980484b72acd373a0350f7bdd90a3c789ea1d821 0.600000000000 1584774 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": 1107177, "vin": [ { "gen": { "height": 1107167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acdb6928dc547e10f9f5aae5980484b72acd373a0350f7bdd90a3c789ea1d821" } } ], "extra": [ 1, 11, 94, 64, 116, 210, 87, 68, 193, 3, 81, 57, 128, 122, 115, 232, 1, 159, 100, 10, 40, 26, 108, 72, 176, 217, 71, 7, 151, 187, 244, 160, 188, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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