Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e75a1dd9880060e187210f60880ce0cd907e974fc15fe68cc458dddd2f1b7cfd

Tx prefix hash: 5ffbc80c9788ff4a951ab7a2ef7812526a616294c3452beb54e5a87cf08b93bf
Tx public key: abb494e6e4ee2934e8e1616431f2e0106adb13f121dff9f7a02bb4b059f1f271
Timestamp: 1700871476 Timestamp [UCT]: 2023-11-25 00:17:56 Age [y:d:h:m:s]: 00:333:02:57:58
Block: 898978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238578 RingCT/type: yes/0
Extra: 01abb494e6e4ee2934e8e1616431f2e0106adb13f121dff9f7a02bb4b059f1f27102110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.644633227000 dcy

stealth address amount amount idx
00: 3517b5aeeedebfca5d2acb969825ff7e20a35319c50cb9e678291940368f4d43 0.644633227000 1355415 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": 898988, "vin": [ { "gen": { "height": 898978 } } ], "vout": [ { "amount": 644633227, "target": { "key": "3517b5aeeedebfca5d2acb969825ff7e20a35319c50cb9e678291940368f4d43" } } ], "extra": [ 1, 171, 180, 148, 230, 228, 238, 41, 52, 232, 225, 97, 100, 49, 242, 224, 16, 106, 219, 19, 241, 33, 223, 249, 247, 160, 43, 180, 176, 89, 241, 242, 113, 2, 17, 0, 0, 0, 11, 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