Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5d46267d9f1c54711559b952f7e26aec820e0bde4f57054caabc1a0edf831cb

Tx prefix hash: bdfd98eb378f6aab4c872902587d46e24c159d0b5eec2fb8c9066dbc754e0cb1
Tx public key: 202aa3c4c82f2d68b758e6f8940a12bf19d8c95720dc9b7a656fd16b7398a3fb
Timestamp: 1696081383 Timestamp [UCT]: 2023-09-30 13:43:03 Age [y:d:h:m:s]: 01:224:05:41:08
Block: 859459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421339 RingCT/type: yes/0
Extra: 01202aa3c4c82f2d68b758e6f8940a12bf19d8c95720dc9b7a656fd16b7398a3fb0211000000054b8f5122000000000000000000

1 output(s) for total of 0.871476333000 dcy

stealth address amount amount idx
00: 4d5633d6468859f973c3a078626e4c871ddf17e0ba4984d27a86967a672123d4 0.871476333000 1313687 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": 859469, "vin": [ { "gen": { "height": 859459 } } ], "vout": [ { "amount": 871476333, "target": { "key": "4d5633d6468859f973c3a078626e4c871ddf17e0ba4984d27a86967a672123d4" } } ], "extra": [ 1, 32, 42, 163, 196, 200, 47, 45, 104, 183, 88, 230, 248, 148, 10, 18, 191, 25, 216, 201, 87, 32, 220, 155, 122, 101, 111, 209, 107, 115, 152, 163, 251, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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