Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89464d4b00eaed53fb322a05e44fb6f2c16ec560fa1b22b8ca31e925e19b888c

Tx prefix hash: aaffc34b165a8f0f1f4cc60cd1066d77e60d76b1cd277061ba7caffef6eed2d8
Tx public key: fb22d628001483b7ca881e6ffccba6f9029470557311a164c74f964dfdddbf7d
Timestamp: 1728453665 Timestamp [UCT]: 2024-10-09 06:01:05 Age [y:d:h:m:s]: 00:107:19:23:49
Block: 1127642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77029 RingCT/type: yes/0
Extra: 01fb22d628001483b7ca881e6ffccba6f9029470557311a164c74f964dfdddbf7d02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee57564934bdf39d8e6d92cb9bd488c34a3c47c66513c7fe7774097bee5e995c 0.600000000000 1610449 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": 1127652, "vin": [ { "gen": { "height": 1127642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee57564934bdf39d8e6d92cb9bd488c34a3c47c66513c7fe7774097bee5e995c" } } ], "extra": [ 1, 251, 34, 214, 40, 0, 20, 131, 183, 202, 136, 30, 111, 252, 203, 166, 249, 2, 148, 112, 85, 115, 17, 161, 100, 199, 79, 150, 77, 253, 221, 191, 125, 2, 17, 0, 0, 0, 2, 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