Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 392fca97d4b3742ca62aa7fa08452364d29cbb7611d8ef93394d1b4f3e219c96

Tx prefix hash: d13293cd7203162ca62a35b54aa7a89a0cb475742705e0c731d7da867d8bb864
Tx public key: 7d262e5ca38b59dcff74425d64a028e1954eb1e23964075d9da7549aee41d614
Timestamp: 1732024815 Timestamp [UCT]: 2024-11-19 14:00:15 Age [y:d:h:m:s]: 00:119:21:41:32
Block: 1157153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85523 RingCT/type: yes/0
Extra: 017d262e5ca38b59dcff74425d64a028e1954eb1e23964075d9da7549aee41d614021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a8937e6f3c5ad9f6739914f7e7e00f1e530c63545adb19e88544e9f71ca2279 0.600000000000 1642776 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": 1157163, "vin": [ { "gen": { "height": 1157153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a8937e6f3c5ad9f6739914f7e7e00f1e530c63545adb19e88544e9f71ca2279" } } ], "extra": [ 1, 125, 38, 46, 92, 163, 139, 89, 220, 255, 116, 66, 93, 100, 160, 40, 225, 149, 78, 177, 226, 57, 100, 7, 93, 157, 167, 84, 154, 238, 65, 214, 20, 2, 17, 0, 0, 0, 2, 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