Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4736f3b597b52a5613838294dc141a0f6e9d18a3d49c53b28eff7eadf0683d1a

Tx prefix hash: 1480390c45ebc6a0ab2a818627c1b381de57a20c96269acc6cdfe8ac7db0c227
Tx public key: 1bf954cd13e7dd65a38dfac667a182b47752d880859d4a98de18a4dc06ba8684
Timestamp: 1735127634 Timestamp [UCT]: 2024-12-25 11:53:54 Age [y:d:h:m:s]: 00:093:06:14:31
Block: 1182853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66432 RingCT/type: yes/0
Extra: 011bf954cd13e7dd65a38dfac667a182b47752d880859d4a98de18a4dc06ba86840211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c107166ae14c9bbf8c403c4c58f6f583631f53cf1790da25b4fa6bcec6adc6b 0.600000000000 1669292 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": 1182863, "vin": [ { "gen": { "height": 1182853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c107166ae14c9bbf8c403c4c58f6f583631f53cf1790da25b4fa6bcec6adc6b" } } ], "extra": [ 1, 27, 249, 84, 205, 19, 231, 221, 101, 163, 141, 250, 198, 103, 161, 130, 180, 119, 82, 216, 128, 133, 157, 74, 152, 222, 24, 164, 220, 6, 186, 134, 132, 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