Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ea146228a6e1457fc1536d1752e2e2b42bd7a14b5fd4dd17fe9cd2e034e28e6

Tx prefix hash: 9542516fc87dbbb7edc3c0239d25b78615891bbe0936cc3fc331a9583e3ef149
Tx public key: 901e0b91dbdb662d3636578c3850bb3bdc3d6e2227fa47e9a602ffc000311373
Timestamp: 1701601970 Timestamp [UCT]: 2023-12-03 11:12:50 Age [y:d:h:m:s]: 01:048:16:41:45
Block: 905026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296139 RingCT/type: yes/0
Extra: 01901e0b91dbdb662d3636578c3850bb3bdc3d6e2227fa47e9a602ffc000311373021100000001faf35c9c000000000000000000

1 output(s) for total of 0.615563902000 dcy

stealth address amount amount idx
00: b8e3bd1ff27e9b130d441359f2fa61c4f9c8b1da89a73bd6f3fee0bf727a5fcd 0.615563902000 1361851 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": 905036, "vin": [ { "gen": { "height": 905026 } } ], "vout": [ { "amount": 615563902, "target": { "key": "b8e3bd1ff27e9b130d441359f2fa61c4f9c8b1da89a73bd6f3fee0bf727a5fcd" } } ], "extra": [ 1, 144, 30, 11, 145, 219, 219, 102, 45, 54, 54, 87, 140, 56, 80, 187, 59, 220, 61, 110, 34, 39, 250, 71, 233, 166, 2, 255, 192, 0, 49, 19, 115, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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