Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b23682318ebb3bcafe1c54dad85ffd77be9a44a033b82eb2db7dfb0b002ac6c

Tx prefix hash: 414f3f9d1d80d8913aeebe205f878c861e4a27283731b94bbb42a6a2ab8ae4a2
Tx public key: 8a19a37b41e2482685e1a2aefd5a377342f8f57015a304c5a3265be23a23556a
Timestamp: 1713844905 Timestamp [UCT]: 2024-04-23 04:01:45 Age [y:d:h:m:s]: 01:003:22:29:38
Block: 1006530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263750 RingCT/type: yes/0
Extra: 018a19a37b41e2482685e1a2aefd5a377342f8f57015a304c5a3265be23a23556a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbe5f45b920ffbeff7c0ee9c7b492ab73c9c85746384ac85b24f6657a97d4f80 0.600000000000 1467588 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": 1006540, "vin": [ { "gen": { "height": 1006530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbe5f45b920ffbeff7c0ee9c7b492ab73c9c85746384ac85b24f6657a97d4f80" } } ], "extra": [ 1, 138, 25, 163, 123, 65, 226, 72, 38, 133, 225, 162, 174, 253, 90, 55, 115, 66, 248, 245, 112, 21, 163, 4, 197, 163, 38, 91, 226, 58, 35, 85, 106, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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