Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f002ffc315fed588e88d1867f24bc2f1a6230dbe17f86e74bb7ace50a2af1bb2

Tx prefix hash: 704362b6deabf9d913b58a712803a2efb0d1a5f3e651266fad7928260321d3a2
Tx public key: 548eb8b7c0ac3135b8ed50c0a292d9abadd07a135dfad59f5501c29e63767e74
Timestamp: 1737580765 Timestamp [UCT]: 2025-01-22 21:19:25 Age [y:d:h:m:s]: 00:145:20:49:56
Block: 1203111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104000 RingCT/type: yes/0
Extra: 01548eb8b7c0ac3135b8ed50c0a292d9abadd07a135dfad59f5501c29e63767e74021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15841a01cbc268f9f5a6837014b504ac96b0bdd4e6e0b7b331b8ff297bca2ad0 0.600000000000 1689784 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": 1203121, "vin": [ { "gen": { "height": 1203111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15841a01cbc268f9f5a6837014b504ac96b0bdd4e6e0b7b331b8ff297bca2ad0" } } ], "extra": [ 1, 84, 142, 184, 183, 192, 172, 49, 53, 184, 237, 80, 192, 162, 146, 217, 171, 173, 208, 122, 19, 93, 250, 213, 159, 85, 1, 194, 158, 99, 118, 126, 116, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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