Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61e2f6340e904b368f7ee75e18111b91d6c0ccd7a50e546b8ba44a2e6d44ba5b

Tx prefix hash: bfabd3a534b6efa38932afbea7b18cd372857b8152635fe39bed3296dd8f6e4c
Tx public key: 82057d5fde864e3aabe9ff971ca29bde5200e1480e99c25a7c8f86d70c43d049
Timestamp: 1706845393 Timestamp [UCT]: 2024-02-02 03:43:13 Age [y:d:h:m:s]: 00:232:19:20:17
Block: 948486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166771 RingCT/type: yes/0
Extra: 0182057d5fde864e3aabe9ff971ca29bde5200e1480e99c25a7c8f86d70c43d04902110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3987ef88db5af6ecc08e4b4d25a324cd6736841118a59c2856acaef7cde065df 0.600000000000 1406904 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": 948496, "vin": [ { "gen": { "height": 948486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3987ef88db5af6ecc08e4b4d25a324cd6736841118a59c2856acaef7cde065df" } } ], "extra": [ 1, 130, 5, 125, 95, 222, 134, 78, 58, 171, 233, 255, 151, 28, 162, 155, 222, 82, 0, 225, 72, 14, 153, 194, 90, 124, 143, 134, 215, 12, 67, 208, 73, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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