Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9ee0e9137488e8940d1e68637a9b21c928b4a0d574f92eadacbcbe870d68b4f

Tx prefix hash: 10e6aa2bbfd07f31aa821358435f14a760ed98e76258fa0fafbc7252f6b97483
Tx public key: f5ee4f23ea906048dd0b456d6ae96077732dcd1fd4133f2e2833f0bf72117d19
Timestamp: 1720397462 Timestamp [UCT]: 2024-07-08 00:11:02 Age [y:d:h:m:s]: 00:201:00:31:15
Block: 1060844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143807 RingCT/type: yes/0
Extra: 01f5ee4f23ea906048dd0b456d6ae96077732dcd1fd4133f2e2833f0bf72117d19021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baeec6aa61d712999a1f895986800ff9646543c4412eb379b9fa9e1e7d39c7f7 0.600000000000 1531331 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": 1060854, "vin": [ { "gen": { "height": 1060844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baeec6aa61d712999a1f895986800ff9646543c4412eb379b9fa9e1e7d39c7f7" } } ], "extra": [ 1, 245, 238, 79, 35, 234, 144, 96, 72, 221, 11, 69, 109, 106, 233, 96, 119, 115, 45, 205, 31, 212, 19, 63, 46, 40, 51, 240, 191, 114, 17, 125, 25, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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