Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57477aa4c8f1ebd0697117780736414d3114fb3fde162373e686c37ad7dcee1d

Tx prefix hash: 0f72b3b34af2de9e6e11b5cc499c4e93cd6235235254c63e4bd688b132823039
Tx public key: e050cfaa0094f82e616a674bbaf4282c1e6559d72ae56bbdac5f9f3d6fa644c6
Timestamp: 1706451422 Timestamp [UCT]: 2024-01-28 14:17:02 Age [y:d:h:m:s]: 01:029:17:52:29
Block: 945202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282318 RingCT/type: yes/0
Extra: 01e050cfaa0094f82e616a674bbaf4282c1e6559d72ae56bbdac5f9f3d6fa644c602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 608621e2146b6aaddfa0bc9d2b001e0fbeb4078f6e7b4eb60acde016f518cc25 0.600000000000 1403512 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": 945212, "vin": [ { "gen": { "height": 945202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "608621e2146b6aaddfa0bc9d2b001e0fbeb4078f6e7b4eb60acde016f518cc25" } } ], "extra": [ 1, 224, 80, 207, 170, 0, 148, 248, 46, 97, 106, 103, 75, 186, 244, 40, 44, 30, 101, 89, 215, 42, 229, 107, 189, 172, 95, 159, 61, 111, 166, 68, 198, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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