Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395c71e4be5fff23225226df3865a5b4f6490fb1f05324aad21276271be82fde

Tx prefix hash: 505e2be0be2205a32fc541699664a0e3246c07c2b85bc40c4b54f6afb807d9ed
Tx public key: 28216e53012192a564a27000eeb0a207b9ad35ea308ce9f15396c0e5a036bd14
Timestamp: 1736908242 Timestamp [UCT]: 2025-01-15 02:30:42 Age [y:d:h:m:s]: 00:154:00:05:38
Block: 1197582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109775 RingCT/type: yes/0
Extra: 0128216e53012192a564a27000eeb0a207b9ad35ea308ce9f15396c0e5a036bd14021100000005e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ba44396574637f9839f9ae717bd29d09b3a82e4746c638a1a85759a26f84849 0.600000000000 1684195 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": 1197592, "vin": [ { "gen": { "height": 1197582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ba44396574637f9839f9ae717bd29d09b3a82e4746c638a1a85759a26f84849" } } ], "extra": [ 1, 40, 33, 110, 83, 1, 33, 146, 165, 100, 162, 112, 0, 238, 176, 162, 7, 185, 173, 53, 234, 48, 140, 233, 241, 83, 150, 192, 229, 160, 54, 189, 20, 2, 17, 0, 0, 0, 5, 228, 220, 144, 9, 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