Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d62ed5f6f970c28dc8289a2ac33de4cbe721aaae0d2bbf3fee6456ccf6ff545c

Tx prefix hash: ffc61f1cc2bcc57576c58529f87cadc6c19a60232c67a26a108f54d989a8beab
Tx public key: de8c53f6907557fa3902615cd7384003db7a0318355baa01b08f8c14a5ad7144
Timestamp: 1709830065 Timestamp [UCT]: 2024-03-07 16:47:45 Age [y:d:h:m:s]: 01:242:21:33:50
Block: 973247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432298 RingCT/type: yes/0
Extra: 01de8c53f6907557fa3902615cd7384003db7a0318355baa01b08f8c14a5ad71440211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c35ba4e6cc62d0a783b11294110061b6d75c3f3a4760fd7b508fa5ccfb9df8c3 0.600000000000 1433182 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": 973257, "vin": [ { "gen": { "height": 973247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c35ba4e6cc62d0a783b11294110061b6d75c3f3a4760fd7b508fa5ccfb9df8c3" } } ], "extra": [ 1, 222, 140, 83, 246, 144, 117, 87, 250, 57, 2, 97, 92, 215, 56, 64, 3, 219, 122, 3, 24, 53, 91, 170, 1, 176, 143, 140, 20, 165, 173, 113, 68, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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