Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92ca429b5dcb6d4588f21a67a943c5000e020071c6700987aa56de58e6791d58

Tx prefix hash: 57bb1fd8332705f5517723392b0a29ca10c560b9364f351700b9511bd09eba5b
Tx public key: e8e1494d843d9050dce46abf4165294f1b8fa48db8fe5f012accec95fb5a1a22
Timestamp: 1725102023 Timestamp [UCT]: 2024-08-31 11:00:23 Age [y:d:h:m:s]: 00:221:17:29:41
Block: 1099852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158324 RingCT/type: yes/0
Extra: 01e8e1494d843d9050dce46abf4165294f1b8fa48db8fe5f012accec95fb5a1a2202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcf280b0b20e173183e2ee421b6169d60ccb0fe0f5c50011a035eecdc9c593c8 0.600000000000 1575821 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": 1099862, "vin": [ { "gen": { "height": 1099852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcf280b0b20e173183e2ee421b6169d60ccb0fe0f5c50011a035eecdc9c593c8" } } ], "extra": [ 1, 232, 225, 73, 77, 132, 61, 144, 80, 220, 228, 106, 191, 65, 101, 41, 79, 27, 143, 164, 141, 184, 254, 95, 1, 42, 204, 236, 149, 251, 90, 26, 34, 2, 17, 0, 0, 0, 4, 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