Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2ed0b920b4c146ddd861aea3831c70c825187863a6f2a0a4ff4e547ad4fa31c

Tx prefix hash: 3a69055e79730647f0efedebcdc2a57324a8d7f4b3b7eca2ced85c39b357e916
Tx public key: 4b157d961f9824be7a702a27916bf1fd1bb4bf4ee20afc68b5d228676edff2d2
Timestamp: 1703170153 Timestamp [UCT]: 2023-12-21 14:49:13 Age [y:d:h:m:s]: 01:126:13:46:37
Block: 918025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351598 RingCT/type: yes/0
Extra: 014b157d961f9824be7a702a27916bf1fd1bb4bf4ee20afc68b5d228676edff2d202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3daaf2921ed9d566aef8192670bcea1f1875dfaf2a7fac0f9a5fcf2b6c540661 0.600000000000 1375661 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": 918035, "vin": [ { "gen": { "height": 918025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3daaf2921ed9d566aef8192670bcea1f1875dfaf2a7fac0f9a5fcf2b6c540661" } } ], "extra": [ 1, 75, 21, 125, 150, 31, 152, 36, 190, 122, 112, 42, 39, 145, 107, 241, 253, 27, 180, 191, 78, 226, 10, 252, 104, 181, 210, 40, 103, 110, 223, 242, 210, 2, 17, 0, 0, 0, 6, 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