Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd4c3ebbbfea1b10716037774d0f70a179fe6c2346a79c100626f994351a550e

Tx prefix hash: a165aa71dcae792ebdb9fb42288d42e5547833123e6d4fea2e67f9d279af3b4e
Tx public key: e2f4bbab7dfdafa5442c9f58d19e690459578b50eff4e0acfd7f2e5bb9de0502
Timestamp: 1713379957 Timestamp [UCT]: 2024-04-17 18:52:37 Age [y:d:h:m:s]: 00:211:05:13:35
Block: 1002663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151221 RingCT/type: yes/0
Extra: 01e2f4bbab7dfdafa5442c9f58d19e690459578b50eff4e0acfd7f2e5bb9de050202110000000e52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18f1df97a30c610cee300704090f64d237ba5e1e18158347ae94380658c52d05 0.600000000000 1463181 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": 1002673, "vin": [ { "gen": { "height": 1002663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18f1df97a30c610cee300704090f64d237ba5e1e18158347ae94380658c52d05" } } ], "extra": [ 1, 226, 244, 187, 171, 125, 253, 175, 165, 68, 44, 159, 88, 209, 158, 105, 4, 89, 87, 139, 80, 239, 244, 224, 172, 253, 127, 46, 91, 185, 222, 5, 2, 2, 17, 0, 0, 0, 14, 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