Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35ea26c599072d7e49d2296e5a2e63563481cc71ca00dc6521c56dbcdb0101ca

Tx prefix hash: 725d5ef5ef38889b8df022be9daa933ebaa71305600258793843ee2bf8ea5eac
Tx public key: 7af75b6d2de910ab1e03f5ce7f4f5f64f25dd4a5a12bfbf3ed0501884c923998
Timestamp: 1711466339 Timestamp [UCT]: 2024-03-26 15:18:59 Age [y:d:h:m:s]: 01:051:16:44:09
Block: 986833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297918 RingCT/type: yes/0
Extra: 017af75b6d2de910ab1e03f5ce7f4f5f64f25dd4a5a12bfbf3ed0501884c92399802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecf298f06d053d64947c7a13dfaca22e07b43b1535c72436ab6833b3358882c9 0.600000000000 1447068 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": 986843, "vin": [ { "gen": { "height": 986833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecf298f06d053d64947c7a13dfaca22e07b43b1535c72436ab6833b3358882c9" } } ], "extra": [ 1, 122, 247, 91, 109, 45, 233, 16, 171, 30, 3, 245, 206, 127, 79, 95, 100, 242, 93, 212, 165, 161, 43, 251, 243, 237, 5, 1, 136, 76, 146, 57, 152, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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