Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3a1d4ed34cfa5ec1d5dc1e3e6d0129d0e975453512d4d2500595751eb6a7af4

Tx prefix hash: 65b102e3cab33f7cc1baa29b332b8612d7b8a677b8ecd650535f78f5ed547394
Tx public key: 592b030140c1015ca8edaabe4ed11e68be490ccdcaa20e2364f41f076d16e3a3
Timestamp: 1673124841 Timestamp [UCT]: 2023-01-07 20:54:01 Age [y:d:h:m:s]: 02:052:21:42:24
Block: 669798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559463 RingCT/type: yes/0
Extra: 01592b030140c1015ca8edaabe4ed11e68be490ccdcaa20e2364f41f076d16e3a302110000000183600029000000000000000000

1 output(s) for total of 3.704086646000 dcy

stealth address amount amount idx
00: 61048379e1d3e963ccc6ba0cc532eb63cefcd2ad710a099de7b51a91cef715fd 3.704086646000 1111157 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": 669808, "vin": [ { "gen": { "height": 669798 } } ], "vout": [ { "amount": 3704086646, "target": { "key": "61048379e1d3e963ccc6ba0cc532eb63cefcd2ad710a099de7b51a91cef715fd" } } ], "extra": [ 1, 89, 43, 3, 1, 64, 193, 1, 92, 168, 237, 170, 190, 78, 209, 30, 104, 190, 73, 12, 205, 202, 162, 14, 35, 100, 244, 31, 7, 109, 22, 227, 163, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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