Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e77ece7526acf1847a1b6034602d3d39aed918c73770d8fbe6b2a4d75baf6fe

Tx prefix hash: 3521adef288dcd0291fa221ca6655e3facb9573ffba6109a7e945df2b7de1a7d
Tx public key: b431a5039cd0043a7dd8e3d0df63b9b65a21468e758198dc768ab89ec8b035d0
Timestamp: 1716041713 Timestamp [UCT]: 2024-05-18 14:15:13 Age [y:d:h:m:s]: 00:190:18:39:47
Block: 1024746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136549 RingCT/type: yes/0
Extra: 01b431a5039cd0043a7dd8e3d0df63b9b65a21468e758198dc768ab89ec8b035d002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6496210626cc1730850bf6033b7cb71f087aeba89e73772939e4ef88ed8e7d0f 0.600000000000 1490733 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": 1024756, "vin": [ { "gen": { "height": 1024746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6496210626cc1730850bf6033b7cb71f087aeba89e73772939e4ef88ed8e7d0f" } } ], "extra": [ 1, 180, 49, 165, 3, 156, 208, 4, 58, 125, 216, 227, 208, 223, 99, 185, 182, 90, 33, 70, 142, 117, 129, 152, 220, 118, 138, 184, 158, 200, 176, 53, 208, 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