Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 888ecb6637fe68533dc37322e7081141a24c0b374a7dc34765119955dbe4860a

Tx prefix hash: 9ee6312425fd845933ed9c0fb67181fb4cb9db874382a5c116b941406d2b1188
Tx public key: 2692a830b5cb9e01befc76c4d54eafac14467715d6770b5196da99e09b86ecb4
Timestamp: 1712509044 Timestamp [UCT]: 2024-04-07 16:57:24 Age [y:d:h:m:s]: 00:361:04:12:03
Block: 995414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258248 RingCT/type: yes/0
Extra: 012692a830b5cb9e01befc76c4d54eafac14467715d6770b5196da99e09b86ecb40211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8947d509b7c47be342fb0e2212032e5e2cbfeb8b8172e31f4f98a051327271e 0.600000000000 1455822 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": 995424, "vin": [ { "gen": { "height": 995414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8947d509b7c47be342fb0e2212032e5e2cbfeb8b8172e31f4f98a051327271e" } } ], "extra": [ 1, 38, 146, 168, 48, 181, 203, 158, 1, 190, 252, 118, 196, 213, 78, 175, 172, 20, 70, 119, 21, 214, 119, 11, 81, 150, 218, 153, 224, 155, 134, 236, 180, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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