Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55c8936cca10cf1fde1b2f832a80ff9be82e82ddb9d8e3fe0c545bba31b15478

Tx prefix hash: a00951e6f5c0a641b6ecd84768e3bcbeff0bdec283f8686a31b561ab2fb04c67
Tx public key: f7f87b462c110e602910a27b860b745ca6b33164136861e5d17058b0ce80bffd
Timestamp: 1726421505 Timestamp [UCT]: 2024-09-15 17:31:45 Age [y:d:h:m:s]: 00:274:21:03:01
Block: 1110788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196221 RingCT/type: yes/0
Extra: 01f7f87b462c110e602910a27b860b745ca6b33164136861e5d17058b0ce80bffd021100000006e914dd15000000000000000000

1 output(s) for total of 0.607960000000 dcy

stealth address amount amount idx
00: 1bebe0b99ef05d595c3169fc2c1de377d46f2c9ceefa3f54a5b24368be46f28b 0.607960000000 1589519 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": 1110798, "vin": [ { "gen": { "height": 1110788 } } ], "vout": [ { "amount": 607960000, "target": { "key": "1bebe0b99ef05d595c3169fc2c1de377d46f2c9ceefa3f54a5b24368be46f28b" } } ], "extra": [ 1, 247, 248, 123, 70, 44, 17, 14, 96, 41, 16, 162, 123, 134, 11, 116, 92, 166, 179, 49, 100, 19, 104, 97, 229, 209, 112, 88, 176, 206, 128, 191, 253, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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