Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57477ae371478f36501cf3358cb326c4b35f129101d5d20332b5af9ef3b94410

Tx prefix hash: 6422d5a72d34666d99e58594e2aa013e36678f90c49eb009d2db6d74acf91c04
Tx public key: d411ba55a8f0379c0b7406ef4c9ff8d844b7dc6cef9694ddd100279cf91dab16
Timestamp: 1673920952 Timestamp [UCT]: 2023-01-17 02:02:32 Age [y:d:h:m:s]: 02:083:18:20:53
Block: 676394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 581532 RingCT/type: yes/0
Extra: 01d411ba55a8f0379c0b7406ef4c9ff8d844b7dc6cef9694ddd100279cf91dab160211000000018b7b6602000000000000000000

1 output(s) for total of 3.522295933000 dcy

stealth address amount amount idx
00: 4e3075017f7c90b2f62c1c4cb44c5d414014e0dd5329a9ec61399b1e6af1edfa 3.522295933000 1118107 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": 676404, "vin": [ { "gen": { "height": 676394 } } ], "vout": [ { "amount": 3522295933, "target": { "key": "4e3075017f7c90b2f62c1c4cb44c5d414014e0dd5329a9ec61399b1e6af1edfa" } } ], "extra": [ 1, 212, 17, 186, 85, 168, 240, 55, 156, 11, 116, 6, 239, 76, 159, 248, 216, 68, 183, 220, 108, 239, 150, 148, 221, 209, 0, 39, 156, 249, 29, 171, 22, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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