Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa4c7b50c3a8c64e47be7ba38c22e66a39174bb491ca235603d058b219fd28e8

Tx prefix hash: d8ffbe4070dd90a708c886b3aec0ca4af1dc7a05755a9a0736ff36a2cd4a3b56
Tx public key: edcc4785351c483c9c3532d07c82fa8e2bd177940020add6a746a346acedad2c
Timestamp: 1705229695 Timestamp [UCT]: 2024-01-14 10:54:55 Age [y:d:h:m:s]: 01:100:17:45:18
Block: 935095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333101 RingCT/type: yes/0
Extra: 01edcc4785351c483c9c3532d07c82fa8e2bd177940020add6a746a346acedad2c0211000000110011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a539527a904db106e501f2cfd7ca6dad0cbd8c975a9e2ae8cd6bc3e77392805 0.600000000000 1393111 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": 935105, "vin": [ { "gen": { "height": 935095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a539527a904db106e501f2cfd7ca6dad0cbd8c975a9e2ae8cd6bc3e77392805" } } ], "extra": [ 1, 237, 204, 71, 133, 53, 28, 72, 60, 156, 53, 50, 208, 124, 130, 250, 142, 43, 209, 119, 148, 0, 32, 173, 214, 167, 70, 163, 70, 172, 237, 173, 44, 2, 17, 0, 0, 0, 17, 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