Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc906e11f37796984c44a2dfc7017d8f2aea5c1fd347aa059d5f05ac870dfc2e

Tx prefix hash: 81636ab7e9c150615eacefd09a2246502c5900aad34341423d6ec6288f7a9b22
Tx public key: 1998695e9719fd3d9fc76acd9e39caf6d94da77304f1162ffc627d5b50e6d5ff
Timestamp: 1728566446 Timestamp [UCT]: 2024-10-10 13:20:46 Age [y:d:h:m:s]: 00:173:23:40:29
Block: 1128568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124150 RingCT/type: yes/0
Extra: 011998695e9719fd3d9fc76acd9e39caf6d94da77304f1162ffc627d5b50e6d5ff02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f708931e211a68de47e35aeec3d9851b52e22c551120e9174e8aed12074fef52 0.600000000000 1611387 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": 1128578, "vin": [ { "gen": { "height": 1128568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f708931e211a68de47e35aeec3d9851b52e22c551120e9174e8aed12074fef52" } } ], "extra": [ 1, 25, 152, 105, 94, 151, 25, 253, 61, 159, 199, 106, 205, 158, 57, 202, 246, 217, 77, 167, 115, 4, 241, 22, 47, 252, 98, 125, 91, 80, 230, 213, 255, 2, 17, 0, 0, 0, 6, 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