Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98535262af82b4057fd6180f52cd32408d11ef6a1b9b1d6a3cd9aab2ad0d6840

Tx prefix hash: babf76b68a6f0899a0be54af9a62edfba5a46b6fa69e857c9d0ea0a1b58843bb
Tx public key: 4e761c4f6d84e7bf3ee54d1d4f591d5e235e815832738f02b2107ea580f3c545
Timestamp: 1704345339 Timestamp [UCT]: 2024-01-04 05:15:39 Age [y:d:h:m:s]: 01:317:14:12:44
Block: 927776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485807 RingCT/type: yes/0
Extra: 014e761c4f6d84e7bf3ee54d1d4f591d5e235e815832738f02b2107ea580f3c54502110000000441ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ac3d16d4993414ef59668b463070d303a2ab81be43a0033322c5a3f12cf964c 0.600000000000 1385612 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": 927786, "vin": [ { "gen": { "height": 927776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ac3d16d4993414ef59668b463070d303a2ab81be43a0033322c5a3f12cf964c" } } ], "extra": [ 1, 78, 118, 28, 79, 109, 132, 231, 191, 62, 229, 77, 29, 79, 89, 29, 94, 35, 94, 129, 88, 50, 115, 143, 2, 178, 16, 126, 165, 128, 243, 197, 69, 2, 17, 0, 0, 0, 4, 65, 238, 28, 155, 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