Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78c419d496310146beeaa5036ca7b895c7f4f0d637c2314016a40867a2619545

Tx prefix hash: d5fe85afe6835eaa326ec25b95505e8a3defc2bc70d219296eb7bfbfe948b7a0
Tx public key: cb0d323a17342132c85abc8867d4da3cbff55daf4e5a8d652a7f2fef52d5dbab
Timestamp: 1719718123 Timestamp [UCT]: 2024-06-30 03:28:43 Age [y:d:h:m:s]: 00:284:23:21:14
Block: 1055206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203641 RingCT/type: yes/0
Extra: 01cb0d323a17342132c85abc8867d4da3cbff55daf4e5a8d652a7f2fef52d5dbab02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 492448f0d2279261dd9f01e53283a139f86ab5a4997ce9978f70d980c5aa4584 0.600000000000 1525603 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": 1055216, "vin": [ { "gen": { "height": 1055206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "492448f0d2279261dd9f01e53283a139f86ab5a4997ce9978f70d980c5aa4584" } } ], "extra": [ 1, 203, 13, 50, 58, 23, 52, 33, 50, 200, 90, 188, 136, 103, 212, 218, 60, 191, 245, 93, 175, 78, 90, 141, 101, 42, 127, 47, 239, 82, 213, 219, 171, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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