Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecf284f8aacca2560e90aafb6f7e86569dac7a8d6563183247a9c24605121125

Tx prefix hash: f1c468ac0f696ac77cd87ac94cb5e2a6885b33ac6722ef45bc487fdfe024c0fc
Tx public key: 7690374c5d23b506748d277da55a2b11355d80643720bad562f656d6d3a72d1f
Timestamp: 1696078497 Timestamp [UCT]: 2023-09-30 12:54:57 Age [y:d:h:m:s]: 01:149:16:17:40
Block: 859438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367996 RingCT/type: yes/0
Extra: 017690374c5d23b506748d277da55a2b11355d80643720bad562f656d6d3a72d1f02110000000b4b8f5122000000000000000000

1 output(s) for total of 0.871615970000 dcy

stealth address amount amount idx
00: 43f1a93bd2e7fefbb024765a6737fff8d943f233940cd478b72bbe46216f5a9e 0.871615970000 1313664 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": 859448, "vin": [ { "gen": { "height": 859438 } } ], "vout": [ { "amount": 871615970, "target": { "key": "43f1a93bd2e7fefbb024765a6737fff8d943f233940cd478b72bbe46216f5a9e" } } ], "extra": [ 1, 118, 144, 55, 76, 93, 35, 181, 6, 116, 141, 39, 125, 165, 90, 43, 17, 53, 93, 128, 100, 55, 32, 186, 213, 98, 246, 86, 214, 211, 167, 45, 31, 2, 17, 0, 0, 0, 11, 75, 143, 81, 34, 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