Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66083e05222938139a2e76e7ece60d1280b5e6603dccfbde35b075a04308f246

Tx prefix hash: 20107d1767fcfc7f8cdfd9480853aa9e42b8894baa414af4faadcd44e19ae3e2
Tx public key: 956176a846d52babcdd85df291b988632dc5c417bf80bfdae82fc60b313f7f36
Timestamp: 1700851522 Timestamp [UCT]: 2023-11-24 18:45:22 Age [y:d:h:m:s]: 01:191:05:35:26
Block: 898808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397878 RingCT/type: yes/0
Extra: 01956176a846d52babcdd85df291b988632dc5c417bf80bfdae82fc60b313f7f36021100000010faf35c9c000000000000000000

1 output(s) for total of 0.645469860000 dcy

stealth address amount amount idx
00: e068835e10a0c97d2c63e8a443596f4c6f981d05d99b977989594be3ef8f32ad 0.645469860000 1355243 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": 898818, "vin": [ { "gen": { "height": 898808 } } ], "vout": [ { "amount": 645469860, "target": { "key": "e068835e10a0c97d2c63e8a443596f4c6f981d05d99b977989594be3ef8f32ad" } } ], "extra": [ 1, 149, 97, 118, 168, 70, 213, 43, 171, 205, 216, 93, 242, 145, 185, 136, 99, 45, 197, 196, 23, 191, 128, 191, 218, 232, 47, 198, 11, 49, 63, 127, 54, 2, 17, 0, 0, 0, 16, 250, 243, 92, 156, 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