Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4dea25c5b647861fa68fd208f9640e6d47d2eb5443362b18e6e5ee8b4675445

Tx prefix hash: 895246594d973833679029e89c9ac43b47ff67322890fb21e83730ebc447f6b2
Tx public key: 037e04a5c0c6f4a6798ef414762f768d8d092d4d38f540e8bb364eed7061a59f
Timestamp: 1715133945 Timestamp [UCT]: 2024-05-08 02:05:45 Age [y:d:h:m:s]: 00:189:08:45:31
Block: 1017213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135551 RingCT/type: yes/0
Extra: 01037e04a5c0c6f4a6798ef414762f768d8d092d4d38f540e8bb364eed7061a59f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a43e368ad0858b88379bddac224f6cc257e1d5fc6d8f92396c9c765028652369 0.600000000000 1480982 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": 1017223, "vin": [ { "gen": { "height": 1017213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a43e368ad0858b88379bddac224f6cc257e1d5fc6d8f92396c9c765028652369" } } ], "extra": [ 1, 3, 126, 4, 165, 192, 198, 244, 166, 121, 142, 244, 20, 118, 47, 118, 141, 141, 9, 45, 77, 56, 245, 64, 232, 187, 54, 78, 237, 112, 97, 165, 159, 2, 17, 0, 0, 0, 2, 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