Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96bf9f58c8438094ef171e7cdc43c813b8d830870857d138536cdeea2a36abd1

Tx prefix hash: 7997cff45ec02b10132d7353d6e2c955da9159550c3068e61ccc010665dfc7e7
Tx public key: 295f08afa5f7e2a0c9cb2935e8759ca6f2caa8d106bebbb417aae52929906e5d
Timestamp: 1697412620 Timestamp [UCT]: 2023-10-15 23:30:20 Age [y:d:h:m:s]: 01:222:00:31:07
Block: 870496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419749 RingCT/type: yes/0
Extra: 01295f08afa5f7e2a0c9cb2935e8759ca6f2caa8d106bebbb417aae52929906e5d02110000000136a45730000000000000000000

1 output(s) for total of 0.801097578000 dcy

stealth address amount amount idx
00: 29a6c9ec90beef5106cf66a5df7f4a17d7721e4b95443b3a0c313c8a15bc3de9 0.801097578000 1325375 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": 870506, "vin": [ { "gen": { "height": 870496 } } ], "vout": [ { "amount": 801097578, "target": { "key": "29a6c9ec90beef5106cf66a5df7f4a17d7721e4b95443b3a0c313c8a15bc3de9" } } ], "extra": [ 1, 41, 95, 8, 175, 165, 247, 226, 160, 201, 203, 41, 53, 232, 117, 156, 166, 242, 202, 168, 209, 6, 190, 187, 180, 23, 170, 229, 41, 41, 144, 110, 93, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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