Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7a4b939ae14d96d9e889969b8738abc220d37def54a188514732f38cddcc69a

Tx prefix hash: 54f7218b7aff78d7e36ecbc2f9bc372ad4a67b7609cf358f965c2829d4b4c2d9
Tx public key: 8c030664a3e4bafecfcfc51c4cb83fa0a8ac51b493be1c971ea9345be2d528ca
Timestamp: 1708560589 Timestamp [UCT]: 2024-02-22 00:09:49 Age [y:d:h:m:s]: 01:115:16:58:32
Block: 962720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343661 RingCT/type: yes/0
Extra: 018c030664a3e4bafecfcfc51c4cb83fa0a8ac51b493be1c971ea9345be2d528ca0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 642b1c13d85487e0b0b24f2663fa5b5a0944e136bf3314d32fda7533c453a78e 0.600000000000 1422403 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": 962730, "vin": [ { "gen": { "height": 962720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "642b1c13d85487e0b0b24f2663fa5b5a0944e136bf3314d32fda7533c453a78e" } } ], "extra": [ 1, 140, 3, 6, 100, 163, 228, 186, 254, 207, 207, 197, 28, 76, 184, 63, 160, 168, 172, 81, 180, 147, 190, 28, 151, 30, 169, 52, 91, 226, 213, 40, 202, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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