Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 493cedd2cd1a5efdb538161d39d6b0fb54e13f1fdf297ebc9f3228c000b503aa

Tx prefix hash: 662f1a15efbfcd34a0a8a6da62078241ee459ae12ac302bf1e9d7563e8d19400
Tx public key: 1b85cf26446c5491ba09f233c0079e52c95ca625f97af7a5e6617200a509dc4d
Timestamp: 1736241985 Timestamp [UCT]: 2025-01-07 09:26:25 Age [y:d:h:m:s]: 00:092:18:11:25
Block: 1192076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66078 RingCT/type: yes/0
Extra: 011b85cf26446c5491ba09f233c0079e52c95ca625f97af7a5e6617200a509dc4d021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d5424b5f144b96fa41b81877a9c1136240c3c0db18f9411ffb89f75bed5a888 0.600000000000 1678621 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": 1192086, "vin": [ { "gen": { "height": 1192076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d5424b5f144b96fa41b81877a9c1136240c3c0db18f9411ffb89f75bed5a888" } } ], "extra": [ 1, 27, 133, 207, 38, 68, 108, 84, 145, 186, 9, 242, 51, 192, 7, 158, 82, 201, 92, 166, 37, 249, 122, 247, 165, 230, 97, 114, 0, 165, 9, 220, 77, 2, 17, 0, 0, 0, 7, 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