Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a99241fc84aef393ee73bdcb00ce7731a7a92af69134ca20c1056feb115ca007

Tx prefix hash: 3265848972cc8d4ccc4ab5d2b27c43a12ad18c7c7ee92a38ec7e3a8146e84109
Tx public key: fcd58dbbdb0932e4c79e3a7f9e2332947750bcda2feacedf8bfb29d72a58d1b6
Timestamp: 1725520441 Timestamp [UCT]: 2024-09-05 07:14:01 Age [y:d:h:m:s]: 00:125:22:06:00
Block: 1103319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90065 RingCT/type: yes/0
Extra: 01fcd58dbbdb0932e4c79e3a7f9e2332947750bcda2feacedf8bfb29d72a58d1b6021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3228d83fa5613c26b024b326950007f6bd7eeabf6d54fa318f5d9e4e65f06dc 0.600000000000 1580102 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": 1103329, "vin": [ { "gen": { "height": 1103319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3228d83fa5613c26b024b326950007f6bd7eeabf6d54fa318f5d9e4e65f06dc" } } ], "extra": [ 1, 252, 213, 141, 187, 219, 9, 50, 228, 199, 158, 58, 127, 158, 35, 50, 148, 119, 80, 188, 218, 47, 234, 206, 223, 139, 251, 41, 215, 42, 88, 209, 182, 2, 17, 0, 0, 0, 3, 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