Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b70ad6b9f64b76fa81ff8a28873845e524fa39bb67c330eaabb370b8418f6faa

Tx prefix hash: ae017b7a3ee7d7d3268d3c875f64b2c793de4fac5ae217c03a2fc11d00bf8713
Tx public key: 59561e0b6954c944008bd8e6b209000a981aa499ae5f3a834a08021553626c01
Timestamp: 1708356423 Timestamp [UCT]: 2024-02-19 15:27:03 Age [y:d:h:m:s]: 01:078:15:17:42
Block: 961029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317240 RingCT/type: yes/0
Extra: 0159561e0b6954c944008bd8e6b209000a981aa499ae5f3a834a08021553626c0102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7f9ee9d0e380647fdff6f95d9cbb1fb4bd396c47adf4d513e122f4fac5f42f9 0.600000000000 1420616 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": 961039, "vin": [ { "gen": { "height": 961029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7f9ee9d0e380647fdff6f95d9cbb1fb4bd396c47adf4d513e122f4fac5f42f9" } } ], "extra": [ 1, 89, 86, 30, 11, 105, 84, 201, 68, 0, 139, 216, 230, 178, 9, 0, 10, 152, 26, 164, 153, 174, 95, 58, 131, 74, 8, 2, 21, 83, 98, 108, 1, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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