Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8285d372e32ed7d4a129fe07617b5ed85779d60839292451c309485af26743e

Tx prefix hash: f5061ae22294f61306bc5703d29e93e6ae7aa06a086774ec3a577b75102f9a1d
Tx public key: bb7c9bb12e89b68ddc59c93fb7760d1433f13cd6dbc1ea739701c88e8a6c2c07
Timestamp: 1706896131 Timestamp [UCT]: 2024-02-02 17:48:51 Age [y:d:h:m:s]: 01:271:07:00:52
Block: 948901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452686 RingCT/type: yes/0
Extra: 01bb7c9bb12e89b68ddc59c93fb7760d1433f13cd6dbc1ea739701c88e8a6c2c07021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b533e85c34555aa89dc53668d010f67605009d2081992b644bb0e3a3a08f162 0.600000000000 1407411 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": 948911, "vin": [ { "gen": { "height": 948901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b533e85c34555aa89dc53668d010f67605009d2081992b644bb0e3a3a08f162" } } ], "extra": [ 1, 187, 124, 155, 177, 46, 137, 182, 141, 220, 89, 201, 63, 183, 118, 13, 20, 51, 241, 60, 214, 219, 193, 234, 115, 151, 1, 200, 142, 138, 108, 44, 7, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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