Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b976ea71224e71c189174681e38746ab40cb800ac800fce14ff4592c450004d3

Tx prefix hash: c3d635ad4dc0e267d6e2af9bc9745d2c1ee77c00d9cfdbc77023be550518e24e
Tx public key: e80a26e99aa1b9e08f18a96b1f09c9a582d0cbf5addfd6f2e5f0a8bc8b208cc8
Timestamp: 1731842132 Timestamp [UCT]: 2024-11-17 11:15:32 Age [y:d:h:m:s]: 00:157:20:00:57
Block: 1155636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112637 RingCT/type: yes/0
Extra: 01e80a26e99aa1b9e08f18a96b1f09c9a582d0cbf5addfd6f2e5f0a8bc8b208cc802110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5eacf96c2d4b7dd5e969af340598fe88054c426ffd2cfd0e229c29c358a6f28 0.600000000000 1641253 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": 1155646, "vin": [ { "gen": { "height": 1155636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5eacf96c2d4b7dd5e969af340598fe88054c426ffd2cfd0e229c29c358a6f28" } } ], "extra": [ 1, 232, 10, 38, 233, 154, 161, 185, 224, 143, 24, 169, 107, 31, 9, 201, 165, 130, 208, 203, 245, 173, 223, 214, 242, 229, 240, 168, 188, 139, 32, 140, 200, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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