Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4aa026e5bd34075405ad48273c10c55e0d5bc73faf006e2664f4c3db8c637142

Tx prefix hash: f2bdfcafcc8d75c065cebf450ec8bb81be4b8a0343ee6b95356749aa605be505
Tx public key: 5c300c64e7bcc4c10ba2583ea6ce55a85fe62c8a92cd63c03982d5e1be517950
Timestamp: 1698333093 Timestamp [UCT]: 2023-10-26 15:11:33 Age [y:d:h:m:s]: 01:087:10:15:32
Block: 878141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323666 RingCT/type: yes/0
Extra: 015c300c64e7bcc4c10ba2583ea6ce55a85fe62c8a92cd63c03982d5e1be5179500211000000054b8f5122000000000000000000

1 output(s) for total of 0.755708572000 dcy

stealth address amount amount idx
00: a49f76a438e8a78ba74039ff85379d837bae175584b3668f30b2dc3567178c74 0.755708572000 1333557 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": 878151, "vin": [ { "gen": { "height": 878141 } } ], "vout": [ { "amount": 755708572, "target": { "key": "a49f76a438e8a78ba74039ff85379d837bae175584b3668f30b2dc3567178c74" } } ], "extra": [ 1, 92, 48, 12, 100, 231, 188, 196, 193, 11, 162, 88, 62, 166, 206, 85, 168, 95, 230, 44, 138, 146, 205, 99, 192, 57, 130, 213, 225, 190, 81, 121, 80, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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