Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 161e2dea0d0f23ac9bf7a8bd041f5e721560b01c5f2a8f10976c6c8802f2846c

Tx prefix hash: 51b3191d1b58591fb82dde50d63e7176682140381719915ede494de7c70a2555
Tx public key: e8d2053d32e9afd90c89d8f9a7806ea2101b9303ad59fed5eb39302d35d4881b
Timestamp: 1708434829 Timestamp [UCT]: 2024-02-20 13:13:49 Age [y:d:h:m:s]: 01:261:15:48:39
Block: 961674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445754 RingCT/type: yes/0
Extra: 01e8d2053d32e9afd90c89d8f9a7806ea2101b9303ad59fed5eb39302d35d4881b02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36d7a6fdebca5c4fc34f4ef6c9981383b9dd4fbcb517d176866c9f786f300527 0.600000000000 1421285 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": 961684, "vin": [ { "gen": { "height": 961674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36d7a6fdebca5c4fc34f4ef6c9981383b9dd4fbcb517d176866c9f786f300527" } } ], "extra": [ 1, 232, 210, 5, 61, 50, 233, 175, 217, 12, 137, 216, 249, 167, 128, 110, 162, 16, 27, 147, 3, 173, 89, 254, 213, 235, 57, 48, 45, 53, 212, 136, 27, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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