Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a1b43582efd8a6d4b61f965d4d069e9a7c5d6ee8df6e782cf71c63fbcd23b28

Tx prefix hash: 22d76368b605479ff47e84062e24a1f5582a1e30ed8658e40f8156a6d0daa248
Tx public key: 570a87c6d3de091a8be4fdf8d2befdabe8d42d2d6d41a68eb78cac7a693ced98
Timestamp: 1737673838 Timestamp [UCT]: 2025-01-23 23:10:38 Age [y:d:h:m:s]: 00:295:00:12:39
Block: 1203881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208387 RingCT/type: yes/0
Extra: 01570a87c6d3de091a8be4fdf8d2befdabe8d42d2d6d41a68eb78cac7a693ced98021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8506af462f5d86418cb5aca529a17030ffe42af192b06600ec9b42e757e823c5 0.600000000000 1690562 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": 1203891, "vin": [ { "gen": { "height": 1203881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8506af462f5d86418cb5aca529a17030ffe42af192b06600ec9b42e757e823c5" } } ], "extra": [ 1, 87, 10, 135, 198, 211, 222, 9, 26, 139, 228, 253, 248, 210, 190, 253, 171, 232, 212, 45, 45, 109, 65, 166, 142, 183, 140, 172, 122, 105, 60, 237, 152, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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