Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4005bdb8c3f111abf38a145f914a662a64f5859bc4a4b1e0b5c63bd88db9bebf

Tx prefix hash: 2f4086656e983a0832cae75603ae2ca59f1b63a2299f14fca18f5291f50a71ce
Tx public key: f05faa3b1689e968ea6cd5d28bcff83ff9b9d24f5384b4f1fa55ea25a89ab430
Timestamp: 1725356045 Timestamp [UCT]: 2024-09-03 09:34:05 Age [y:d:h:m:s]: 00:215:19:44:58
Block: 1101965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154076 RingCT/type: yes/0
Extra: 01f05faa3b1689e968ea6cd5d28bcff83ff9b9d24f5384b4f1fa55ea25a89ab43002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3efeaf955bd32813016c8dee289a62aa97e0fc19e66ce2fab57417c7a3718e2 0.600000000000 1578216 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": 1101975, "vin": [ { "gen": { "height": 1101965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3efeaf955bd32813016c8dee289a62aa97e0fc19e66ce2fab57417c7a3718e2" } } ], "extra": [ 1, 240, 95, 170, 59, 22, 137, 233, 104, 234, 108, 213, 210, 139, 207, 248, 63, 249, 185, 210, 79, 83, 132, 180, 241, 250, 85, 234, 37, 168, 154, 180, 48, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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