Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00902798b29e41e10dc972dab995bf8f5454a1b5897ef28648c43268887492be

Tx prefix hash: 63938966f34d0235285248a766fac32f0d7e7b76bfa8aed56626fd90f1e91d92
Tx public key: 4c1012d9f487b60ac1963a9fc5265ae28b6342c2238b8a80cf6fdfd2df76246a
Timestamp: 1696733475 Timestamp [UCT]: 2023-10-08 02:51:15 Age [y:d:h:m:s]: 02:044:19:28:44
Block: 864875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551654 RingCT/type: yes/0
Extra: 014c1012d9f487b60ac1963a9fc5265ae28b6342c2238b8a80cf6fdfd2df76246a02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.836199942000 dcy

stealth address amount amount idx
00: 0cd43c163e89f723da446ab287857d0b9e0a76eae6c6110705d6242d56c50fae 0.836199942000 1319397 of 0

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": 864885, "vin": [ { "gen": { "height": 864875 } } ], "vout": [ { "amount": 836199942, "target": { "key": "0cd43c163e89f723da446ab287857d0b9e0a76eae6c6110705d6242d56c50fae" } } ], "extra": [ 1, 76, 16, 18, 217, 244, 135, 182, 10, 193, 150, 58, 159, 197, 38, 90, 226, 139, 99, 66, 194, 35, 139, 138, 128, 207, 111, 223, 210, 223, 118, 36, 106, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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