Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a3deecded30c994d6e1730b0359bcf40e4fbacc18cf362b98e8b2338d978685

Tx prefix hash: d1b3d622e3aa59a11f660fffbb1457a9d6190bd396476374e86bcca2dc8aa4a9
Tx public key: b668a686bd7e71545ae5a14b0bb47e007b96cb13de46a808a5867280829c9e7d
Timestamp: 1736844102 Timestamp [UCT]: 2025-01-14 08:41:42 Age [y:d:h:m:s]: 00:155:03:36:35
Block: 1197057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110596 RingCT/type: yes/0
Extra: 01b668a686bd7e71545ae5a14b0bb47e007b96cb13de46a808a5867280829c9e7d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84567eb5539595a074eb20a64aef92a02b2a214afcc39beab38c532f073ad4a0 0.600000000000 1683662 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": 1197067, "vin": [ { "gen": { "height": 1197057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84567eb5539595a074eb20a64aef92a02b2a214afcc39beab38c532f073ad4a0" } } ], "extra": [ 1, 182, 104, 166, 134, 189, 126, 113, 84, 90, 229, 161, 75, 11, 180, 126, 0, 123, 150, 203, 19, 222, 70, 168, 8, 165, 134, 114, 128, 130, 156, 158, 125, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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